System and method of allocating computing resources based on jurisdiction

ABSTRACT

In one or more embodiments, one or more processes, methods, and/or systems associated with a first jurisdiction may receive a request for a transaction, that involves private information, from a second computer system in a second jurisdiction. For example, the second jurisdiction may be subject to one or more privacy statutes and/or one or more privacy regulations. For instance, the one or more privacy statutes and/or one or more privacy regulations may apply to entities outside the jurisdiction that collect and/or process data of a resident and/or a citizen of the jurisdiction. In one or more embodiments, the one or more processes, methods, and/or systems may further determine that the second computer system is in the second jurisdiction, provide an instruction to a third computer system, in the second jurisdiction, to execute program instructions that executes the transaction, and receive, from the third computer system, metadata associated with the transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/618,925 filed Jun. 9, 2017, by Jisoo Lee, and entitled “System andMethod of Allocating Computing Resources based on Jurisdiction,” whichis incorporated herein by reference.

TECHNICAL FIELD

Certain embodiments of this disclosure relate generally to distributedcomputer systems and more particularly to allocating computing resourcesbased on jurisdiction.

BACKGROUND

Networks allow users to access various types of computing resources,which may include hardware resources and/or software resources. Examplesof hardware resources include computer networks, servers, memory, and soon. Examples of software resources include applications, services, data,and so on. In distributed computing systems, such as cloud-basedsystems, a user may be allocated computing resources on a temporarybasis. For example, the user may be allocated computing resources inorder to complete a transaction. Certain transactions may require thecommunication of private information. The computing resources may beconfigured to provide encryption and/or other security measures to helpprotect the privacy of such information. In some cases, one or moreprivacy statutes and/or privacy regulations may require that thecomputing resources comply with certain security measures.

SUMMARY

In one or more embodiments, one or more processes, methods, and/orsystems associated with a first jurisdiction may receive a request for atransaction, that involves private information, from a second computersystem in a second jurisdiction. For example, the second jurisdictionmay be subject to one or more privacy statutes and/or one or moreprivacy regulations. For instance, the one or more privacy statutesand/or one or more privacy regulations may apply to entities outside thejurisdiction that collect and/or process data of a resident and/or acitizen of the jurisdiction. In one or more embodiments, the one or moreprocesses, methods, and/or systems may determine that the secondcomputer system is in the second jurisdiction, may provide aninstruction to a third computer system, in the second jurisdiction, toexecute program instructions that executes the transaction, and mayreceive, from the third computer system, metadata associated with thetransaction. In one example, at least one of a container and a virtualmachine may include the program instructions to execute the transaction.In another example, the metadata may include at least one of atransaction identification, a receipt, and time information. In oneinstance, the transaction may include a commercial transaction. Inanother instance, the transaction may include a banking transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsfeatures/advantages, reference is now made to the following description,taken in conjunction with the accompanying drawings, which are not drawnto scale, and in which:

FIG. 1 illustrates an example of a computer system, according to one ormore embodiments;

FIG. 2 illustrates an example of computer systems coupled to a network,according to one or more embodiments;

FIG. 3 illustrates an example of a forum that receives metadata andcompensation information, according to one or more embodiments;

FIG. 4 illustrates an example of a forum that receives containers andvirtual machines, according to one or more embodiments;

FIG. 5 provides a block diagram illustrating an example of distributingcontainers to computer systems, according to one or more embodiments;

FIG. 6 provides a block diagram illustrating an example of distributingvirtual machines to computer systems, according to one or moreembodiments;

FIG. 7 provides a block diagram illustrating an example of distributingvirtual machines and containers to computer systems, according to one ormore embodiments;

FIG. 8 illustrates an example of a method of providing processorinstructions to at least one computer device, according to one or moreembodiments;

FIG. 9 illustrates example computer systems coupled to multiple networksin respective multiple jurisdictions, according to one or moreembodiments; and

FIG. 10 illustrates an example of a method of conducting a transaction,according to one or more embodiments.

DETAILED DESCRIPTION

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are for purposes of example and are not exhaustiveof all possible embodiments.

As used herein, a reference numeral followed by a letter refers to aspecific instance of an element and the numeral only form of thereference numeral refers to the collective element. Thus, for example,device ‘12A’ refers to an instance of a device class, which may bereferred to collectively as devices ‘12’ and any one of which may bereferred to generically as a device ‘12’.

In distributed computing systems, such as cloud-based systems, computingresources can be geographically distributed. Accordingly, it may bepossible to allocate resources associated with one geographical locationto a user in another geographical location. In certain situations, thesegeographical locations may be distributed across multiple jurisdictions.Examples of jurisdictions include one or more states, countries, orother types of jurisdictions (e.g., European Union). A jurisdiction canbe subject to one or more privacy statutes and/or one or more privacyregulations, and the one or more privacy statutes and/or one or moreprivacy regulations can apply to entities outside the jurisdiction thatcollect and/or process data of a resident and/or a citizen of thejurisdiction. Even though the entities are outside the jurisdiction, theentities may conduct business in the jurisdiction, and the one or moreprivacy statutes and/or the one or more privacy regulations can includea requirement that private information, of a resident and/or a citizenof the jurisdiction, is not transferred outside the jurisdiction.Private information can include personal data, and the personal data mayinclude information relating to an individual, such as financialinformation, health information, personally identifiable information(e.g., social security number), etc. Certain embodiments of the presentdisclosure may provide solutions for allocating computing resources of ageographically distributed computing system in a manner that allows forcompliance with privacy statutes and privacy regulations of theapplicable jurisdiction.

In one or more embodiments, one or more privacy statutes and/or one ormore privacy regulations may include a requirement that a transactionthat involves a citizen of the jurisdiction occurs within thejurisdiction. In one example, the transaction may include a commercialtransaction. In another example, the transaction may include a bankingtransaction. In one or more embodiments, private information may includepersonal data, and the personal data may include information relating toan individual. For example, the information relating to the individualmay include information related to a private life, a professional life,and/or a public life of the individual. For instance, the informationrelating to the individual may include one or more of a home address, aphoto, an email address, a name, a banking detail, medical information,a post on a social network, and an Internet protocol (IP) address of acomputer system, among others.

In one or more embodiments, a first computer system within ajurisdiction may be permitted to provide private information to a secondcomputer system within the jurisdiction, and the second computer systemmay provide the private information and/or metadata associated with theprivate information to a third computer system outside the jurisdiction.For example, one or more statutes and/or one or more regulations maypermit the first computer system within the jurisdiction providing, viaa network within the jurisdiction, the private information to the secondcomputer system within the jurisdiction. In one or more embodiments, thesecond computer system may provide metadata, associated with utilizingand/or processing the private information, to a third computer systemoutside the jurisdiction. For example, a transaction may utilize and/orprocess the private information. For instance, the transaction mayinclude one or more of a banking transaction, a sales transaction, afinancial transaction, a stock transaction, a property transaction, anda commercial transaction, among others, and metadata associated with thetransaction may be provided to the third computer system outside thejurisdiction.

In one or more embodiments, the third computer system outside thejurisdiction may receive, via a network, a request for a transactionfrom the first computer system. For example, the third computer systemmay provide, via the network, an instruction to the second computersystem, within the jurisdiction, to execute program instructions thatexecutes the transaction. For example, the first computer system and thesecond computer system may execute the transaction, and the secondcomputer system may provide metadata associated with the transaction tothe third computer system. In one or more embodiments, the thirdcomputer system may provide a branded look and feel to the secondcomputer system. For example, an entity that owns and/or controls thethird computer system may provide may provide a branded look and feel ofthe entity to the second computer system. In one or more embodiments,the program instructions that executes the transaction may include thebranded look and feel of the entity. For example, the programinstructions, that executes the transaction, may provide the brandedlook and feel of the entity to a user of the first computer system.

In one or more embodiments, computing resources, such as computersystems or portions thereof, may be utilized to perform variouscomputer-oriented operations, such as performing computations,processing information, classifying data, routing data, detecting athreshold, receiving data, recording data, providing data, producingdata, and reproducing data, among others. The computing resources may beutilized during one or more periods of time and idle during otherperiods of time. During the idle periods, the computing resources can beshut down or left powered with no computer-oriented operations toperform, which may result in the computing resources being non-utilizedor under utilized. Embodiments of the present disclosure may allowcomputing resources that might otherwise be non-utilized or underutilized to be made available to one or more entities for compensation.

In one or more embodiments, computing resources may be made available toone or more entities. In one example, an entity may be or include one ormore of a person, multiple people, a corporation, multiple corporations,a government, multiple governments, a department of a government, andmultiple departments of a government, among others. In one or moreembodiments, the computing resources may be made available to one ormore entities for compensation. For example, by making the computingresources available to one or more entities for compensation, microclouds may be implemented that provide shared computer processingresources that might otherwise be non-utilized or under utilized. In oneinstance, a micro cloud may refer to computing resources that may beutilized, as a secondary purpose, for compensation by other entities. Inanother instance, users of the micro clouds may not be limited to thespecific applications offered via grid computing solutions and mayutilize specific applications and/or architectures of choice.

In one or more embodiments, an entity may offer computing resources forcompensation via a forum. In one instance, a corporation may offer, viathe forum, computing resources that would otherwise be idle or shutdownwhen not utilized for performing computer-oriented operations. Inanother instance, a person or a family may offer, via the forum,computing resources that would otherwise be idle or shutdown at night orduring another time period (e.g., while the person or one or more familymembers are at a place of employment).

In one or more embodiments, a forum may include and/or provide computingresources that are offered compensation and/or computing resources thatare offered for trade. For example, two or more entities may exchangecomputing resources via a form that allows computing resources to beoffered for trade. In one or more embodiments, the forum may becompensated for the exchange of computing resources. As examples, theforum may be compensated by one or more of the entities on asubscription basis, on a flat fee basis (e.g., per allocation or perperiod of use of a computing resource or type of computing resource), asa percentage of the amount of compensation paid by the user of thecomputing resource to the owner of the computing resource, or othersuitable compensation.

In one or more embodiments, metadata that includes computing resourcesthat are offered, for compensation and/or for trade, may be stored andprovided via the forum. For example, the metadata may include one ormore of a number of computer systems, one or more rates of processinginstructions, one or more operating system identifications, one or moreversions corresponding to the one or more operating systemidentifications, one or more sizes of volatile storages, one or moresizes of non-volatile storages, one or more data communication rates,one or more data communication latencies, one or more data communicationthroughputs, one or more geographical locations, one or more networklocations, and/or one or more cache sizes, among others.

In one or more embodiments, an entity may utilize a computing resource.For example, the entity may execute program instructions via thecomputing resource. In one or more embodiments, the program instructionsmay be packaged and/or encapsulated via one or more containers. Forexample, a container may be or include software in a file system thatincludes one or more of instructions executable by a processor (e.g., aprogram, software, an application, server software, a service, etc.),one or more runtime libraries, one or more system tools, and one or moresystem libraries, among others. For instance, a container may be orinclude a Docker container, a Linux container (LXC), or a Kubernetespod, among others. In one or more embodiments, a container may provideand/or implement operating system-level virtualization via a virtualenvironment that includes a separate process and network space, ratherthan creating and/or implementing a virtual machine. In one or moreembodiments, OpenShift may be utilized. For example, OpenShift mayinclude a version of Kubernetes that is supported by Red Hat, Inc. Inone or more embodiments, containers may be more conducive to microservices. For example, micro services may be more conducive to microclouds.

In one or more embodiments, Kubernetes may be utilized in providing oneor more containers to one or more computer systems. In one example,Kubernetes may include a system that may automate deployment of one ormore containers to one or more computer systems. In another example,Kubernetes may provide and/or permit scaling and/or management ofcontainerized applications. For instance, Kubernetes may provide and/orpermit scaling and/or management one or more of containers with one ormore computer systems.

Turning now to FIG. 1, an example of a computer system is illustrated,according to one or more embodiments. As shown, a computer system 1010may include a processor 1100, a volatile memory medium 1200, anon-volatile memory medium 1300, a network interface 1400, and aninput/output (I/O) subsystem 1500. As illustrated, volatile memorymedium 1200, non-volatile memory medium 1300, network interface 1400,and I/O subsystem 1500 may be communicatively coupled to processor 1100.

As shown, non-volatile memory medium 1300 may include an operatingsystem (OS) 1310, applications (APPs) 1320-1322, virtual machines (VMs)1330-1332, a hypervisor (HV) 1340, and containers 1350-1352. In one ormore embodiments, one or more of OS 1310, APPs 1320-1322, VMs 1330-1332,HV 1340, and containers 1350-1352 may include instructions executable byprocessor 1100. In one example, processor 1100 may execute instructionsof one or more of OS 1310, APPs 1320-1322, VMs 1330-1332, HV 1340, andcontainers 1350-1352 via non-volatile memory medium 1300. In anotherexample, one or more portions of the instructions of the one or more ofOS 1310, APPs 1320-1332, VMs 1330-1332, HV 1340, and containers1350-1352 may be transferred to volatile memory medium 1200, andprocessor 1100 may execute the one or more portions of the instructionsof the one or more of OS 1310, APPs 1320-1332, VMs 1330-1332, HV 1340,and containers 1350-1352 via volatile memory medium 1200.

In one or more embodiments, HV 1340 may include one or more of software,firmware, and hardware that creates and executes one or more VMs (e.g.,one or more of VMs 1330-1332). For example, computer system 1010 may beconsidered host machine when HV 1340 executes and one or more of VMs1330-1332 are executed via HV 1340. For instance, a virtual machine (VM)(e.g., a VM of VMs 1330-1332) may be considered a guest machine. In oneor more embodiments, a VM may provide one or more structures and/orfunctionalities as those described with reference to computer system1010 (e.g., singularly or via nesting of hypervisors and virtualmachines). In one example, the VM may provide emulated devices to aguest OS that executes via the VM. In another example, the VM mayprovide hardware devices to the guest OS that executes via the VM. Inone instance, the guest OS may access hardware in a pass-throughconfiguration. In another instance, the guest OS may access hardware ina single root input/output virtualization (SR-IOV) configuration. In oneor more embodiments, guest operating systems may share one or moredevices of a host machine. For example, the guest operating systems mayshare one or more of a network adapter via virtual network adapters anda storage device via a virtual storage devices (e.g., virtual disks,virtual memory, etc.), among others.

In one or more embodiments, OS level virtualization may be utilized. Forexample, OS level virtualization may include a kernel of an OS thatpermits multiple isolated user space instances of collections ofprocesses (e.g., programs, applications, services, etc.). For instance,these instances are often referred to as “containers”, “softwarecontainers”, “virtualization engines”, or “jails” (e.g., FreeBSD jails,chroot jails, etc.). In one or more embodiments, with OS levelvirtualization, an OS may behave and/or may appear like multipledifferent, individual computer systems. For example, little to nooverhead may be imposed by OS level virtualization, as processes in OSlevel virtual partitions may utilize a single system call interface ofan OS. For instance, OS level virtual partitions may not be subjected toemulation or be executed via virtual machines. In one or moreembodiments, OS level virtualization may be utilized in consolidatingcomputer system hardware or virtual machines by moving services onseparate hosts or virtual machines into containers on a computer systemor single virtual machine.

In one or more embodiments, a container may be or include software in afile system that includes one or more of instructions executable by aprocessor (e.g., a program, software, an application, server software, aservice, etc.), one or more runtime libraries, one or more system tools,and one or more system libraries, among others. For example, a containermay be or include a Docker container, a LXC, or a Kubernetes pod, amongothers. In one or more embodiments, a container may provide and/or mayimplement operating system-level virtualization via a virtualenvironment that includes a separate process space and/or a separatenetwork space, rather than creating and/or implementing a virtualmachine.

In one or more embodiments, a container may be or include a pod (e.g., aKubernetes pod). For example, a pod may provide and/or add a higherlevel of abstraction to one or more containerized elements. Forinstance, a pod may include one or more containers that may be warrantedto be co-located and/or executed on a computer system (e.g., a hostcomputer system, host machine, etc.) and may share resources of thecomputer system. In one or more embodiments, a thick container may be orinclude a pod, and a thin container may include a single container.

In one or more embodiments, containers may provide and/or offer animmutable quality and/or option. For example, a container may bedeployed, destroyed, modified, re-constructed and/or re-created, andre-deployed. In one instance, instructions, executable by a processor,of a container may not be modified while the container is executing. Inanother instance, instructions, executable by a processor, of acontainer may not be modified once the container is created.

In one or more embodiments, the term “memory medium” may mean a “memorydevice”, a “memory”, a “storage device”, a “tangible computer readablestorage medium”, and/or a “computer-readable medium”. In one example, amemory medium may be a volatile memory medium. For instance, thevolatile memory medium may lose stored data when the volatile memorymedium no longer receives power. In a second example, a memory mediummay be a non-volatile memory medium. For instance, the non-volatilememory medium may not lose stored data when the volatile memory mediumno longer receives power or when power is not applied. In anotherexample, a memory medium may include a volatile memory medium and anon-volatile memory medium.

In one or more embodiments, a volatile memory medium may includevolatile storage. For example, the volatile storage may include randomaccess memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), and/orextended data out RAM (EDO RAM), among others. In one or moreembodiments, a non-volatile memory may include non-volatile storage. Forexample, the non-volatile storage may include read only memory (ROM),programmable ROM (PROM), erasable PROM (EPROM), electrically erasablePROM (EEPROM), a magnetic storage medium (e.g., a hard drive, a floppydisk, a magnetic tape, etc.), ferroelectric RAM (FRAM), flash memory, asolid state drive (SSD), non-volatile RAM (NVRAM), a one-timeprogrammable (OTP) memory, and/or optical storage (e.g., a compact disc(CD), a digital versatile disc (DVD), a BLU-RAY disc (BD), etc.), amongothers.

In one or more embodiments, I/O subsystem 1500 may include or representa variety of communication interfaces, graphics interfaces, videointerfaces, user input interfaces, and/or peripheral interfaces, amongothers. For example, I/O subsystem 1500 may include one or more of atouch screen, a display, a display adapter, and a universal serial bus(USB) interface, among others. For instance, a touch screen may includecircuitry that enables touch functionality in conjunction with a displaythat is driven by a display adapter.

In one or more embodiments, network interface 1400 may be configured tobe coupled to a network. For example, network interface 1400 may permitcomputer system 1010 to be communicatively coupled to a network. In oneinstance, network interface 1400 may be configured to be coupled to awired network. In a second instance, network interface 1400 may beconfigured to be coupled to a wireless network. In a second instance,network interface 1400 may be configured to be coupled to an opticalnetwork.

In one or more embodiments, one or more of volatile memory medium 1200,non-volatile memory medium 1300, network interface 1400, and I/Osubsystem 1500 may be communicatively coupled to processor 1100 via oneor more buses. For example, a bus may include one or more of aperipheral component interconnect (PCI) bus, a serial peripheralinterface (SPI) bus, an inter-integrated circuit (I²C) bus, an enhancedserial peripheral interface (eSPI) bus, a system management bus (SMBus),a universal serial bus, and a low pin count (LPC) bus, among others. Inone or more embodiments, one or more of volatile memory medium 1200,non-volatile memory medium 1300, network interface 1400, and I/Osubsystem 1500 may be communicatively coupled to processor 1100 via oneor more of a PCI-Express (PCIe) root complex and one or more PCIeswitches, among others.

In one or more embodiments, processor 1100 may execute instructions inimplementing one or more systems, flowcharts, methods, and/or processesdescribed herein. In one example, processor 1100 may execute processorinstructions from one or more of memory media 1200 and 1300 inimplementing one or more systems, flowcharts, methods, and/or processesdescribed herein. In another example, processor 1100 may executeinstructions received via network interface 1400 in implementing one ormore systems, flowcharts, methods, and/or processes described herein.

In one or more embodiments, processor 1100 may include circuitry thatmay interpret and/or execute program instructions and/or process data,among others. For example, processor 1100 may include one or more of asystem, a device, and an apparatus that may interpret and/or executeprogram instructions and/or process data, among others. For instance,processor 1100 may include one or more of a central processing unit(CPU), a microprocessor, a graphics processing unit (GPU), anapplication processor, a digital signal processor (DSP), and anapplication specific integrated circuit (ASIC), among others.

Turning now to FIG. 2, computer systems coupled to a network areillustrated, according to one or more embodiments. As shown, computersystems 1010A-1010K may be communicatively coupled to a network 2010. Inone or more embodiments, network 2010 may include one or more of a wirednetwork, an optical network, and a wireless network. For example,network 2010 may include one or more of a local area network (LAN), awide area network (WAN), a wireless LAN (WLAN), a metropolitan areanetwork (MAN), a public switched telephone network (PSTN), a public WAN(e.g., an Internet), a private WAN, a cellular telephone network, asatellite telephone network, and a virtual private network (VPN), amongothers. In one or more embodiments, network 2010 may be coupled to oneor more other networks. For example, network 2010 may be coupled to oneor more of a LAN, a WAN, a WLAN, a MAN, a PSTN, a public WAN, a privateWAN, a cellular telephone network, a satellite telephone network, and aVPN, among others.

Turning now to FIG. 3, a forum that receives metadata and compensationinformation is illustrated, according to one or more embodiments. Asshown, a forum 3110 may receive metadata 3010-3017. In one or moreembodiments, one or more of metadata 3010-3017 may include one or moreof a number of computer systems, one or more rates of processinginstructions, one or more operating system identifications, one or moreversions corresponding to the one or more operating systemidentifications, one or more sizes of volatile storages, one or moresizes of non-volatile storages, one or more data communication rates,one or more data communication latencies, one or more data communicationthroughputs, one or more geographical locations, one or more networklocations, and/or one or more cache sizes, among others. In one or moreembodiments, forum 3110 may store metadata 3010-3017 via metadata 3120.For example, metadata 3010-3017 may be stored via a database.

In one or more embodiments, one or more of metadata 3010-3017 may bereceived from one or more entities that offer one or more computingresources for compensation and/or for trade. For example, the one ormore entities that offer the one or more computing resources forcompensation and/or for trade may provide, to forum 3110, a number ofcomputer systems, one or more rates of processing instructions, one ormore operating system identifications, one or more versionscorresponding to the one or more operating system identifications, oneor more sizes of volatile storages, one or more sizes of non-volatilestorages, one or more data communication rates, one or more datacommunication latencies, one or more data communication throughputs, oneor more geographical locations, one or more network locations, and/orone or more cache sizes, among others.

In one or more embodiments, one or more of metadata 3010-3017 may bereceived from one or more network providers that provide networkservices to computing resources of one or more entities that offer oneor more computing resources for compensation and/or for trade. Forexample, the one or more network providers may provide one or more datacommunication rates, one or more data communication latencies, one ormore data communication throughputs, one or more geographical locations,and/or one or more network locations, among others. For instance, anetwork location may include where, on a network topology, a computingresource is available.

As illustrated, forum 3110 may receive compensation information3230-3237. In one or more embodiments, one or more of compensationinformation 3230-3237 may include compensation desires and/orrequirements for utilization of one or more computing resources that areoffered. In one example, one or more of compensation information3230-3237 may include one or more minimum compensations for respectiveone or more computing resources. For instance, a computing resource mayinclude a single computer system or multiple computer systems. Inanother example, one or more of compensation information 3230-3237 mayinclude one or more trading information. For instance, the tradinginformation may include information associated with one or more of aservice, a time period, and a physical object, among others, forutilization of a single computer system or multiple computer systems.

In one or more embodiments, multiple entities may trade computingresources. For example, computing resources of two entities may belocated across a planet (e.g., Earth). For instance, computing resourcesof a first entity of the two entities may be traded during a nighttimeperiod to a second entity of the two entities to utilize during adaytime period of the second entity and vice versa.

In one or more embodiments, forum 3110 may store compensationinformation 3230-3237 via compensation information 3220. For example,compensation information 3230-3237 may be stored via a database. In oneor more embodiments, forum 3110 may include a computer system thatincludes one or more structures and/or functionalities as thosedescribed with reference to computer system 1010. In one or moreembodiments, forum 3110 may include multiple computer systems. Forexample, forum 3110 may include two or more of computer systems1010A-1010H, among others.

Turning now to FIG. 4, a forum that receives containers and virtualmachines is illustrated, according to one or more embodiments. As shown,forum 3110 may receive containers 4010-4017. As illustrated, forum 3110may receive virtual machines 4020-4027. In one or more embodiments, anentity may execute program instructions via a computing resource and maypackage and/or encapsulate the program instructions via one or morecontainers and/or via one or more virtual machines. In one example, oneor more entities may provide, to forum 3110, one or more of containers4010-4017 to be executed via computing resources that are offered forcompensation and/or for trade. For instance, the one or more entitiesmay provide, to forum 3110, one or more of containers 4010-4017 vianetwork 2010. In one or more embodiments, forum 3110 may storecontainers 4010-4017 via a container storage 4120. In another example,one or more entities may provide, to forum 3110, one or more of virtualmachines 4020-4027 to be executed via computing resources that areoffered for compensation and/or for trade. For instance, the one or moreentities may provide, to forum 3110, one or more of virtual machines4020-4027 via network 2010. In one or more embodiments, forum 3110 maystore virtual machines 4020-4027 via a virtual machine storage 4220.

Turning now to FIG. 5, a block diagram of distributing containers tocomputer systems is illustrated, according to one or more embodiments.As shown, forum 3110 may provide containers 4010 and 4011 to computersystem 1010A. In one or more embodiments, forum 3110 may providecontainers 4010 and 4011 to computer system 1010A via network. Forexample, the network may be or include network 2010. As illustrated,forum 3110 may provide container 4011 to computer system 1010B. In oneor more embodiments, forum 3110 may provide container 4011 to computersystem 1010B via a network. For example, the network may be or includenetwork 2010. As shown, forum 3110 may provide containers 4011, 4013,4015, and 4017 to computer system 1010C. In one or more embodiments,forum 3110 may provide containers 4011, 4013, 4015, and 4017 to computersystem 1010C via a network. For example, the network may be or includenetwork 2010.

In one or more embodiments, Kubernetes may be utilized in providing oneor more of containers 4010-4017 to one or more of computer systems1010A-1010H. In one example, Kubernetes may include a system that mayautomate deployment of one or more of containers 4010-4017 to one ormore of computer systems 1010A-1010H. In another example, Kubernetes mayprovide and/or permit scaling and/or management of containerizedapplications. For instance, Kubernetes may provide and/or permit scalingand/or management of one or more of containers 4010-4017 with one ormore of computer systems 1010A-1010H.

In one or more embodiments, one or more of computer systems 1010A-1010C,among others, may be included in one or more computing resources thatare offered for compensation and/or trade. For example, one or moreentities may own and/or control one or more of computer systems1010A-1010C, among others. In one instance, a first entity may permitcomputer system 1010A to receive and execute containers 4010 and 4011and may permit computer system 1010B to receive and execute container4011. In a second instance, a second entity, different from the firstentity, may permit computer system 1010C to receive and executecontainers 4011, 4013, 4015, and 4017. In a third instance, the firstentity may permit computer system 1010C to receive and executecontainers 4011, 4013, 4015, and 4017. In a fourth instance, a thirdentity, different from the first entity and the second entity, may beassociated with container 4010, and the third entity may executecontainer 4010 via computer system 1010A. In another instance, a fourthentity, different from the first entity, the second entity, and thethird entity, may be associated with container 4011, and the fourthentity may execute container 4011 via computer systems 1010A-1010C. Inone or more embodiments, one or more of computer systems 1010A-1010C,among others, may receive one or more of containers 4010-4017, amongothers, via network 2010.

Turning now to FIG. 6, a block diagram of distributing virtual machinesto computer systems is illustrated, according to one or moreembodiments. As shown, forum 3110 may provide virtual machines 4210 and4211 to computer system 1010A. In one or more embodiments, forum 3110may provide virtual machines 4210 and 4211 to computer system 1010A vianetwork. For example, the network may be or include network 2010. Asillustrated, forum 3110 may provide virtual machine 4211 to computersystem 1010B. In one or more embodiments, forum 3110 may provide virtualmachine 4211 to computer system 1010B via a network. For example, thenetwork may be or include network 2010. As shown, forum 3110 may providevirtual machines 4211, 4213, 4215, and 4217 to computer system 1010C. Inone or more embodiments, forum 3110 may provide virtual machines 4211,4213, 4215, and 4217 to computer system 1010C via a network. Forexample, the network may be or include network 2010.

In one or more embodiments, one or more of computer systems 1010A-1010C,among others, may be included in one or more computing resources thatare offered for compensation and/or trade. For example, one or moreentities may own and/or control one or more of computer systems1010A-1010C, among others. In one instance, a first entity may permitcomputer system 1010A to receive and execute virtual machines 4210 and4211 and may permit computer system 1010B to receive and execute virtualmachine 4211. In a second instance, a second entity, different from thefirst entity, may permit computer system 1010C to receive and executevirtual machines 4211, 4213, 4215, and 4217. In a third instance, thefirst entity may permit computer system 1010C to receive and executevirtual machines 4211, 4213, 4215, and 4217. In a fourth instance, athird entity, different from the first entity and the second entity, maybe associated with virtual machine 4210, and the third entity mayexecute virtual machine 4210 via computer system 1010A. In anotherinstance, a fourth entity, different from the first entity, the secondentity, and the third entity, may be associated with virtual machine4211, and the fourth entity may execute virtual machine 4211 viacomputer systems 1010A-1010C. In one or more embodiments, one or more ofcomputer systems 1010A-1010C, among others, may receive one or more ofvirtual machines 4210-4217, among others, via network 2010.

Turning now to FIG. 7, a block diagram of distributing virtual machinesand containers to computer systems is illustrated, according to one ormore embodiments. As shown, forum 3110 may provide virtual machines7010-7012 to computer systems 1010A-1010C, respectively. In one or moreembodiments, forum 3110 may provide virtual machines 7010-7012 tocomputer systems 1010A-1010C, respectively, via a network. For example,the network may be or include network 2010.

In one or more embodiments, one or more of virtual machines 7010-7012may provide a computing environment that one or more of containers4010-4017 may execute. For example, one or more of virtual machines7010-7012 may provide a computing environment where one or more ofcontainers 4010-4017 may execute regardless of an underlying OS and/orregardless of underlying hardware of one or more of computer systems1010A-1010C. For instance, one or more of virtual machines 7010-7012 mayprovide a consistent computing environment where one or more ofcontainers 4010-4017 may execute. In one or more embodiments, one ormore of virtual machines 7010-7012 may be utilized with one or morerespective hypervisors. In one example, forum 3110 may provide the oneor more respective hypervisors to respective one or more of computersystems 1010A-1010C. In another example, respective one or more ofcomputer systems 1010A-1010C may include the one or more respectivehypervisors. In one instance, respective one or more of computer systems1010A-1010C may include the one or more respective hypervisors beforerespective virtual machines 7010-7012 are received. In another instance,respective one or more of computer systems 1010A-1010C may include theone or more respective virtual machines 7010-7012 before one or more ofcontainers 4010-4017 are received.

As illustrated, forum 3110 may provide containers 4010 and 4011 tovirtual machine 7010. In one or more embodiments, forum 3110 may providecontainers 4010 and 4011 to virtual machine 7010 via network. Forexample, the network may be or include network 2010. As illustrated,forum 3110 may provide container 4011 to virtual machine 7011. In one ormore embodiments, forum 3110 may provide container 4011 to virtualmachine 7011 via a network. For example, the network may be or includenetwork 2010. As shown, forum 3110 may provide containers 4011, 4013,4015, and 4017 to virtual machine 7012. In one or more embodiments,forum 3110 may provide containers 4011, 4013, 4015, and 4017 to virtualmachine 7012 via a network. For example, the network may be or includenetwork 2010.

In one or more embodiments, Kubernetes may be utilized in providing oneor more of containers 4010-4017 to one or more of virtual machines7010-7012. In one example, Kubernetes may include a system that mayautomate deployment of one or more of containers 4010-4017 to one ormore of virtual machines 7010-7012. In another example, Kubernetes mayprovide and/or permit scaling and/or management of containerizedapplications. For instance, Kubernetes may provide and/or permit scalingand/or management of one or more of containers 4010-4017 with one ormore of virtual machines 7010-7012.

In one or more embodiments, one or more of computer systems 1010A-1010C,among others, may be included in one or more computing resources thatare offered for compensation and/or trade. For example, one or moreentities may own and/or control one or more of computer systems1010A-1010C, among others. In one instance, a first entity may permitcomputer system 1010A to receive and execute containers 4010 and 4011,via virtual machine 7010, and may permit computer system 1010B toreceive and execute container 4011, via virtual machine 7011. In asecond instance, a second entity, different from the first entity, maypermit computer system 1010C to receive and execute containers 4011,4013, 4015, and 4017, via virtual machine 7012. In a third instance, thefirst entity may permit computer system 1010C to receive and executecontainers 4011, 4013, 4015, and 4017, via virtual machine 7012. In afourth instance, a third entity, different from the first entity and thesecond entity, may be associated with container 4010, and the thirdentity may execute container 4010 via computer system 1010A, via virtualmachine 7010. In another instance, a fourth entity, different from thefirst entity, the second entity, and the third entity, may be associatedwith container 4011, and the fourth entity may execute container 4011via computer systems 1010A-1010C, via respective virtual machines7010-7012. In one or more embodiments, one or more of virtual machines7010-7012, among others, may receive one or more of containers4010-4017, among others, via network 2010.

In one or more embodiments, execution of two or more instructionsexecuted by a processor may be performed concurrently. In one example,two or more of containers 4010-4017 may be executed concurrently. Forinstance, a portion of a first container of containers 4010-4017 and aportion of a second container, different from the first container, ofcontainers 4010-4017 may be executed concurrently. In another example,two or more of virtual machines 4200-4217 may be executed concurrently.For instance, a portion of a first virtual machine of virtual machines4200-4217 and a portion of a second virtual machine, different from thefirst virtual machine, of virtual machines 4200-4217 may be executedconcurrently. In one or more embodiments, concurrently may meansimultaneously. In one or more embodiments, concurrently may meanapparently simultaneously according to some metric. In one or moreembodiments, concurrently may mean that execution of a portion of afirst container of containers 4010-4017 and execution of a portion of asecond container, different from the first container, of containers4010-4017 appear to be simultaneous to a human. In one or moreembodiments, concurrently may mean that execution of a portion of afirst virtual machine of virtual machines 4200-4217 and execution of aportion of a second virtual machine, different from the first virtualmachine, of virtual machines 4200-4217 appear to be simultaneous to ahuman.

Turning now to FIG. 8, a method of providing processor instructions toat least one computer device is illustrated, according to one or moreembodiments. At 8010, a computing resource specification that specifiesa minimum computing resource and a preferred compensation may bereceived via a network. For example, forum 3110 may receive thecomputing resource specification via network 2010. For instance, forum3110 may include one or more of computer systems 1010A-1010H that arecommunicatively coupled to network 2010. In one or more embodiments, theminimum computing resource may include a minimum rate of processinginstructions, an operating system identification, an operating systemversion, a minimum storage size (e.g., a size of volatile storage and/ora size of non-volatile storage), a minimum data communication rate, aminimum data communication latency, a minimum data communicationthroughput, a geographical location, a network location, a minimum cachesize, and/or other computing resource.

At 8020, at least one computer system may be determined, from metadatathat includes information associated with multiple computer systems,that fulfills the minimum computing resources of the computing resourcespecification and associated with at least one compensation proximate tothe preferred compensation. For example, forum 3110 may determine atleast one computer system, from metadata that includes informationassociated with multiple computer systems, that fulfills the minimumcomputing resources of the computing resource specification andassociated with at least one compensation proximate to the preferredcompensation.

In one or more embodiments, determining at least one computer system,from metadata that includes information associated with multiplecomputer systems, that fulfills the minimum computing resources of thecomputing resource specification and associated with at least onecompensation proximate to the preferred compensation may includesearching metadata 3120 and compensation information 3220 to determineat least one computer system that fulfills the minimum computingresources of the computing resource specification and associated with atleast one compensation proximate to the preferred compensation. Forexample, forum 3110 may determine one or more computer systems thatfulfill the minimum computing resources of the computing resourcespecification and associated with one or more compensations within arange of compensation (e.g., proximate to the preferred compensation)below and/or above the preferred compensation.

At 8030, computing resource information associated with the at least onecomputer system and the at least one compensation proximate to thepreferred compensation may be provided via the network. For example,forum 3110 may provide, via network 2010, the computing resourceinformation associated with the at least one computer system and the atleast one compensation proximate to the preferred compensation. Forinstance, forum 3110 may provide, via network 2010, the computingresource information to a computer system (e.g., a computer system ofcomputer systems 1010A-1010H) from which the computing resourcespecification was received. In one or more embodiments, the computingresource information associated with the at least one computer systemand the at least one compensation proximate to the preferredcompensation may be included in a web page. For example, forum 3110 mayprovide the web page to a computer system (e.g., a computer system ofcomputer systems 1010A-1010H) via network 2010.

At 8040, information that selects the at least one computer system maybe received via the network. For example, forum 3110 may receive, vianetwork 2010, information that selects the at least one computer system.For instance, the information that selects the at least one computersystem may select one or more of computer systems 1010A-1010H. In one ormore embodiments, information that selects the at least one computersystem may be received via a web server. For example, forum 3110 mayinclude the web server.

At 8050, compensation information utilizable in providing compensationfor utilization of the at least one computer system may be received viathe network. For example, forum 3110 may receive, via network 2010,compensation information utilizable in providing compensation forutilization of the at least one computer system. In one example, thecompensation information utilizable in providing compensation forutilization of the at least one computer system may include paymentinformation. For instance, the payment information may include one ormore account numbers that are utilizable in transferring one or morepayments and/or one or more funds from a first account to a secondaccount. In another example, the compensation information utilizable inproviding compensation for utilization of the at least one computersystem may include trading information. For instance, the tradinginformation may include information associated with one or more of aservice, a time period, and a physical object, among others, forutilization of a single computer system or multiple computer systems.

At 8060, first instructions executable by a processor of the at leastone computer system may be received via the network. For example, forum3110 may receive, via network 2010, first instructions executable by aprocessor of the at least one computer system. In one instance, thefirst instructions may include one or more of containers 4010-4017and/or one or more of virtual machines 4200-4217, among others. Inanother instance, one or more of containers 4010-4017 and/or one or moreof virtual machines 4200-4217 may include the first instructions.

At 8070, the first instructions, executable by the processor of the atleast one computer system, may be provided, via the network, to the atleast one computer system. For example, forum 3110 may provide, vianetwork 2010, the first instructions, executable by the processor of theat least one computer system, to the at least one computer system. Inone or more embodiments, after the first instructions are provided tothe at least one computer system, the first instructions may beimmutable. For example, the first instructions may be immutable whilethe first instructions are stored by the at least one computer system.

At 8080, second instructions executable by the processor of the at leastone computer system may be received via the network. For example, forum3110 may receive, via network 2010, second instructions executable bythe processor of the at least one computer system. In one instance, thesecond instructions may include one or more of containers 4010-4017and/or one or more of virtual machines 4200-4217, among others. Inanother instance, one or more of containers 4010-4017 and/or one or moreof virtual machines 4200-4217 may include the second instructions.

In one or more embodiments, utilizing different containers and/ordifferent virtual machines may provide a level of isolation betweenand/or among two or more different containers and/or different virtualmachines. In one example, an isolation and/or a separation of processes(e.g., programs, applications, services, etc.) between and/or among twoor more different containers and/or different virtual machines may beimplemented via utilizing different containers and/or different virtualmachines. In another example, an isolation and/or a separation of filesystems between and/or among two or more different containers and/ordifferent virtual machines may be implemented via utilizing differentcontainers and/or different virtual machines. For instance, reads fromand/or writes to identically named portions of two different filesystems of two different containers and/or two different virtualmachines may be different and/or directed to different the two differentfile systems.

In one or more embodiments, a combination of containers may be utilizedin isolating different services. For example, a first container mayinclude a web server, and a second container may include a databaseserver. For instance, the web server of the first container may provideone or more database queries to the database server of the secondcontainer, and the database server of the second container may provideone or more results to the web server of the first container.

At 8090, the second instructions, executable by the processor of the atleast one computer system, may be provided, via the network, to the atleast one computer system. For example, forum 3110 may provide, vianetwork 2010, the second instructions, executable by the processor ofthe at least one computer system, to the at least one computer system.In one or more embodiments, after the second instructions are providedto the at least one computer system, the second instructions may beimmutable. For example, the second instructions may be immutable whilethe second instructions are stored by the at least one computer system.

At 8100, the compensation information utilizable in providing thecompensation for utilization of the at least one computer system may beprovided to a computer system of a financial institution. For example,forum 3110 may provide the compensation information utilizable inproviding the compensation for utilization of the at least one computersystem to a computer system of a financial institution. In one instance,the compensation information may include a bank account number. Inanother instance, the compensation information may include a credit cardnumber.

Turning now to FIG. 9, example computer systems coupled to multiplenetworks in respective multiple jurisdictions are illustrated, accordingto one or more embodiments. As shown, computer systems 1010A, 1010E, and1010F may be coupled to a network 9110A in a jurisdiction 9010A;computer systems 1010B, 1010G, and 1010H may be coupled to a network9110B in a jurisdiction 9010B; computer systems 1010C and 1010I-1010Kmay be coupled to a network 9110C in a jurisdiction 9010C; and computersystem 1010D may be coupled to a network 9110D in a jurisdiction 9010D.As illustrated, networks 9110A-9110D may be coupled to network 2010. Inone or more embodiments, one or more of networks 9110A-9110D may includeone or more structures and/or functionalities described with referenceto network 2010.

In one or more embodiments, a jurisdiction may be subject to one or moreprivacy statutes and/or one or more privacy regulations. In one example,the one or more privacy statutes and/or one or more privacy regulationsmay apply to entities outside the jurisdiction that collect and/orprocess data of a resident and/or a citizen of the jurisdiction. In asecond example, the one or more privacy statutes and/or the one or moreprivacy regulations may include a requirement that private information,of a resident and/or a citizen of the jurisdiction, is not transferredoutside the jurisdiction. For instance, the requirement that privateinformation of the citizen of the jurisdiction is not transferredoutside the jurisdiction may stipulate that the private information ofthe citizen of the jurisdiction is not transferred outside thejurisdiction utilizing a public network, such as an Internet. In anotherexample, the one or more privacy statutes and/or the one or more privacyregulations may include a requirement that a transaction that involves acitizen of the jurisdiction occurs within the jurisdiction. In oneinstance, the transaction may include a commercial transaction. Inanother instance, the transaction may include a banking transaction.

In one or more embodiments, private information may include personaldata, and the personal data may include information relating to anindividual. For example, the information relating to the individual mayinclude information related to a private life, a professional life,and/or a public life of the individual. For instance, the informationrelating to the individual may include one or more of a home address, aphoto, an email address, a name, a banking detail, medical information,a post on a social network, and an IP address of a computer system,among others.

In one or more embodiments, a jurisdiction may have and/or may besubject to one or more statutes and/or regulations that may not permit acomputer system to directly provide, via a network, private informationto a computer system outside the jurisdiction. In one example, computersystem 1010E may not be permitted to directly provide, via a network,private information to computer system 1010D. In a second example,computer system 1010G may not be permitted to directly provide, via anetwork, private information to computer system 1010D. In anotherexample, computer system 1010F may not be permitted to directly provide,via a network, private information to computer system 1010K.

In one or more embodiments, a first computer system within ajurisdiction may be permitted to provide private information to a secondcomputer system within the jurisdiction, and the second computer systemmay provide the private information to a third computer system outsidethe jurisdiction. For example, one or more statutes and/or one or moreregulations may permit the first computer system within the jurisdictionproviding, via a network within the jurisdiction, the privateinformation to the second computer system within the jurisdiction. Inone instance, computer system 1010E may be permitted to directlyprovide, via network 9110A, private information to computer system1010A, and computer system 1010A may provide the private information tocomputer system 1010D. In a second instance, computer system 1010G maybe permitted to directly provide, via network 9110B, private informationto computer system 1010B, and computer system 1010B may provide theprivate information to computer system 1010D. In another instance,computer system 1010F may be permitted to directly provide, via network9110A, private information to computer system 1010A, and computer system1010A may provide the private information to computer system 1010K.

Turning now to FIG. 10, an example method of conducting a transaction isillustrated, according to one or more embodiments. At 10010, a firstcomputer system within a first jurisdiction may receive, via a network,a request for a transaction from a second computer system within asecond jurisdiction. In one example, the first computer system may becomputer system 1010D within jurisdiction 9010D. For instance, computersystem 1010D may be or may include one or more computer systems. In asecond example, the second computer system may be computer system 1010Ewithin jurisdiction 9010A, computer system 1010F within jurisdiction9010A, computer system 1010G within jurisdiction 9010B, computer system1010H within jurisdiction 9010B, computer system 1010I withinjurisdiction 9010C, computer system 1010J within jurisdiction 9010C, orcomputer system 1010K within jurisdiction 9010C, among others. Inanother example, the first computer system may be computer system 1010Kwithin jurisdiction 9010C, and the second computer system may becomputer system 1010F within jurisdiction 9010A. In one or moreembodiments, the transaction may include one or more of a bankingtransaction, a sales transaction, a financial transaction, a stocktransaction, a property transaction, and a commercial transaction, amongothers.

At 10020, the first computer system may determine that the secondcomputer system is within the second jurisdiction. In one example,determining that the second computer system is within the secondjurisdiction may include receiving information from the second computersystem that indicates that the second computer system is within thesecond jurisdiction. In one instance, the information from the secondcomputer system may include an address of a user of the second computersystem. In another instance, the information from the second computersystem may include a network address (e.g., an IP address, a telephonenumber, a X.25 address, etc.), which may be utilizable in determiningthat the second computer system is within the second jurisdiction. Inanother example, determining that the second computer system is withinthe second jurisdiction may include utilizing account information. Inone instance, the account information may indicate that the secondcomputer system is within the second jurisdiction. In another instance,the account information may include a physical address that may beutilizable in determining that the second computer system is within thesecond jurisdiction.

At 10030, the first computer system may provide, via the network, aninstruction to a third computer system, within the second jurisdiction,to execute program instructions that executes the transaction. In oneexample, the third computer system may be computer system 1010A withinjurisdiction 9010A. In a second example, the third computer system maybe computer system 1010B within jurisdiction 9010B. In another example,the third computer system may be computer system 1010C withinjurisdiction 9010C.

In one or more embodiments, method element 10030 may be performed inresponse to a determination that the second jurisdiction is subject toone or more privacy statutes and/or one or more privacy regulations, viautilizing metadata that indicates that the second jurisdiction issubject to one or more privacy statutes and/or one or more privacyregulations. In one example, the second jurisdiction may be subject toone or more privacy statutes and/or one or more privacy regulationswhich may apply to entities outside the second jurisdiction that collectand/or process data of a resident and/or a citizen of the secondjurisdiction. In a second example, the second jurisdiction may besubject to one or more privacy statutes and/or one or more privacyregulations, which may require that the computing resources comply withcertain security measures. For instance, the computing resourcesutilized for a transaction may need to occur within the secondjurisdiction. In one or more embodiments, further transaction requestsmay be received, and an entity that controls and/or owns the firstcomputer system may establish a physical presence of one or morecomputer systems within the second jurisdiction. For example, thefurther transaction requests may reach a threshold within an amount oftime transpiring.

In one or more embodiments, the first computer system may provide abranded look and feel to the third computer system. For example, anentity that owns and/or controls the first computer system may providemay provide a branded look and feel of the entity to the third computersystem. In one or more embodiments, the program instructions thatexecutes the transaction may include the branded look and feel of theentity. For example, the program instructions, that executes thetransaction, may provide the branded look and feel of the entity to auser of the second computer system.

In one or more embodiments, the program instructions that executes thetransaction may include or be included in a container. In one example,the program instructions that executes the transaction may include or beincluded in one or more of containers 4010 and 4011, which may executewithin jurisdiction 9010A. In a second example, the program instructionsthat executes the transaction may include or be included in container4011, which may execute within jurisdiction 9010B. In another example,the program instructions that executes the transaction may include or beincluded in one or more of containers 4011, 4013, 4015, and 4017, whichmay execute within jurisdiction 9010C.

In one or more embodiments, the program instructions that executes thetransaction may include or be included in a virtual machine. In oneexample, the program instructions that executes the transaction mayinclude or be included in one or more of virtual machines 4210 and 4211,which may execute within jurisdiction 9010A. In a second example, theprogram instructions that executes the transaction may include or beincluded in virtual machine 4211, which may execute within jurisdiction9010B. In another example, the program instructions that executes thetransaction may include or be included in one or more of virtualmachines 4211, 4213, 4215, and 4217, which may execute withinjurisdiction 9010C.

In one or more embodiments, the third computer system may receive one ormore containers and/or one or more virtual machines from a forum or fromthe first computer system. In one example, the third computer system mayreceive the one or more containers and/or the one or more virtualmachines from forum 3110 (e.g., illustrated in FIGS. 5-7). For instance,a fourth computer system may include forum 3110. In another example, thefirst computer system may be substituted for forum 3110 (e.g.,illustrated in FIGS. 5-7) or may include forum 3110.

At 10040, the third computer system may execute the programinstructions. In one example, the third computer system (e.g., computersystem 1010A) may execute one or more of containers 4010 and 4011, whichmay execute within jurisdiction 9010A. In a second example, the thirdcomputer system (e.g., computer system 1010B) may execute container4011, which may execute within jurisdiction 9010B. In a third example,the third computer system (e.g., computer system 1010C) may execute oneor more of containers 4011, 4013, 4015, and 4017, which may executewithin jurisdiction 9010C. In a fourth example, the third computersystem (e.g., computer system 1010A) may execute one or more of virtualmachines 4210 and 4211, which may execute within jurisdiction 9010A. Ina fifth example, the third computer system (e.g., computer system 1010B)may execute virtual machine 4211, which may execute within jurisdiction9010B. In another example, the third computer system (e.g., computersystem 1010C) may execute one or more of virtual machines 4211, 4213,4215, and 4217, which may execute within jurisdiction 9010C.

At 10050, the third computer system may receive private information fromthe second computer system. For example, the third computer system mayreceive private information from the second computer system via anetwork within the second jurisdiction. For instance, the privateinformation may not leave, exit, and/or depart from the secondjurisdiction. At 1060, the third computer system may execute thetransaction. For example, the third computer system may utilize theprivate information in executing the transaction.

At 10070, the third computer system may provide metadata associated withthe transaction to the first computer system. In one example, themetadata associated with the transaction may include an indication thatthe transaction was successful or unsuccessful. In another example, themetadata associated with the transaction may include one or more of atransaction identification (ID), a receipt, and time information (e.g.,date, time of day, etc.), among others. At 10080, the third computersystem may delete the private information. For example, deleting theprivate information may include destroying the private information. Forinstance, destroying the private information may include overwriting theprivate information with other information.

At 10090, the first computer system may provide one or more goods and/orone or more services based on the metadata. In one example, providingone or more goods and/or one or more services based on the metadata mayinclude providing one or more instructions to ship one or more goods.For instance, one or more goods may have been purchased via the thirdcomputer system, and the first computer system may provide instructionsto ship the purchased goods. In a second example, providing one or moregoods and/or one or more services based on the metadata may includeproviding one or more streaming downloads to the second computer system.For instance, the first computer system may provide instructions toanother computer system to permit providing one or more streamingdownloads to one or more of the second computer system, a video displaysystem, and a digital music player, among others. In another example,providing one or more goods and/or one or more services based on themetadata may include providing one or more instructions to transferfunds from a first account to a second account.

In one or more embodiments, one or more of the method and/or processelements and/or one or more portions of a method and/or processorelements may be performed in varying orders, may be repeated, or may beomitted. Furthermore, additional, supplementary, and/or duplicatedmethod and/or process elements may be implemented, instantiated, and/orperformed as desired, according to one or more embodiments. Moreover,one or more of system elements may be omitted and/or additional systemelements may be added as desired, according to one or more embodiments.

In one or more embodiments, a memory medium may be and/or may include anarticle of manufacture. For example, the article of manufacture mayinclude and/or may be a software product and/or a program product. Forinstance, the memory medium may be coded and/or encoded withprocessor-executable instructions in accordance with one or moreflowcharts, systems, methods, and/or processes described herein toproduce the article of manufacture.

In one or more embodiments, the above-described systems, processes,and/or methods may be used to support e-commerce sites. In e-commerce,for example, the location of the transaction is often important. Forinstance, the European Union currently has significant restrictionsabout the type of private information that cannot leave thejurisdiction. Thus, computing resources handling such privateinformation may be required to be located within the European Union.Because e-commerce sites can exist anywhere in the world, for instance,it may be difficult to comply with jurisdiction-specific requirements.For example, even if the e-commerce home site is located outside thejurisdiction, the information that a customer provides may need tocomply with local requirements of the jurisdiction in which the customeris located.

To address these requirements, one or more embodiments of the presentdisclosure may permit and/or allow for spinning up to a microcloudwithin the jurisdiction in order to provide a local copy an e-commercewebsite of an e-commerce provider. For example, spinning up a microcloudmay permit and/or allow the e-commerce provider to provide services tocustomers within a jurisdiction without requiring a separate hosting.For instance, the e-commerce provider may wait to obtain separatehosting within a particular jurisdiction until the e-commerce providerobtains and/or acquires a critical mass of customers in thatjurisdiction. Thus, the e-commerce provider may not need to heavilyinvest in separate, jurisdiction-specific hosting that might otherwisebe required to comply with all of the regulations and/or statutes of thejurisdiction only to discover that there may not be that many customersin that jurisdiction, currently or in the future.

One or more embodiments may make use of a reverse proxy configuration.For example, the e-commerce site may determine where a requestoriginated and may utilize that information to leverage resources off ofa public cloud that has access to a microcloud within the jurisdiction.For instance, the local microcloud may be spun up to support a localcopy of the application requested by a customer in order to proxy theapplication locally. In one or more embodiments, the microcloudresources may be obtained using a cloud service broker that may permitand/or allow the e-commerce site to specify privacy requirements ofthird party computing resources that will be used to spin up themicrocloud. After completing the transaction, for example, themicrocloud may be configured to destroy private information receivedduring the transaction. For instance, a minimal amount of information(that does not include private information) may be retained by thee-commerce site.

In one or more embodiments, the microcloud may include a container(e.g., thin container or thick container) and/or a virtual machine.Further, one or more embodiments may permit and/or allow for buildingcontainers in different jurisdictions and tailoring the containers tothe specific needs of that jurisdiction. As one example, ajurisdiction-specific container may be configured to use a type ofencryption required by that jurisdiction.

In certain embodiments, a customer may submit a request that wouldrequire spinning up computing resources within a jurisdiction that theparty receiving the request, such as an e-commerce provider, does nothave existing compute/systems (or does not have sufficient computingresources to handle the request). In response to such situations,certain embodiments dynamically create and archive the necessarycompute, storage, and other systems, for example, based on the meta datadetermined from the requested transactions and rules/regulationsapplicable to that jurisdiction. As additional transactions and requestsoriginate from that jurisdiction, the party receiving the transactionsand requests can decide to further dynamically expand and/or decide toestablish permanent/dedicated infrastructure within that jurisdiction.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present disclosure. Thus, to the maximumextent allowed by law, the scope of the present disclosure is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A system, comprising: a hardware processor; and amemory medium that is coupled to the processor and that includesinstructions executable by the processor; wherein the system is in afirst jurisdiction and as the processor executes the instructions, thesystem: receives a request for a transaction from a second computersystem; determines that the second computer system is in a secondjurisdiction, wherein determining that the second computer system is inthe second jurisdiction comprises receiving a network address of thesecond computer system; determines that the second jurisdiction issubject to a privacy law; in response to determining that the secondjurisdiction is subject to the privacy law: selects, from a plurality ofcomputer systems in the second jurisdiction, a third computer system, inthe second jurisdiction, to execute the transaction; provides, to thethird computer system, in the second jurisdiction, at least one of acontainer and a virtual machine that includes program instructions toexecute the transaction; provides an instruction to the third computersystem to execute the program instructions that executes thetransaction, wherein: in response to executing the program instructionsthat execute the transaction, the third computer system receives privateinformation from the second computer system and uses the privateinformation to complete the transaction; receives, from the thirdcomputer system, metadata associated with the transaction, wherein: themetadata comprises an indication that the transaction was successful;and in response to providing the metadata to the system, the thirdcomputer system deletes the private information; and in response toreceiving the metadata, provides at least one of one or more goods andone or more services to the citizen of the second jurisdiction, based onthe metadata.
 2. The system of claim 1, wherein the program instructionsthat executes the transaction include a branded look and feel.
 3. Thesystem of claim 1, wherein the privacy law includes a requirement thatthe transaction that involves the private information of a citizen ofthe second jurisdiction occurs within the second jurisdiction.
 4. Thesystem of claim 1, wherein when the system provides, to the thirdcomputer system, the at least one of the container and the virtualmachine, the system provides the at least one of the container and thevirtual machine to a fourth computer system that stores the at least oneof the container and the virtual machine and provides the container tothe third computer system.
 5. The system of claim 1, wherein when thesystem receives the request for the transaction from the second computersystem in the second jurisdiction, the system determines that the secondjurisdiction is subject to the privacy law, based on metadata of therequest.
 6. The system of claim 1, wherein the second computer systemand the third computer system communicate via a network within thesecond jurisdiction.
 7. The system of claim 1, wherein the metadataincludes a transaction identification, a receipt, and/or timeinformation.
 8. A method, comprising: a first computer system in a firstjurisdiction receiving a request for a transaction from a secondcomputer system; the first computer system determining that the secondcomputer system is in a second jurisdiction, wherein determining thatthe second computer system is in the second jurisdiction comprisesreceiving a network address of the second computer system; the firstcomputer system determining that the second jurisdiction is subject to aprivacy law; in response to determining that the second jurisdiction issubject to the privacy law: the first computer system selecting, from aplurality of computer systems in the second jurisdiction, a thirdcomputer system, in the second jurisdiction, to execute the transaction;the first computer system providing, to the third computer system, inthe second jurisdiction, at least one of a container and a virtualmachine that includes program instructions to execute the transaction;the first computer system providing an instruction to the third computersystem to execute the program instructions that executes thetransaction, wherein: in response to executing the program instructionsthat execute the transaction, the third computer system receives privateinformation from the second computer system and uses the privateinformation to complete the transaction; the first computer systemreceiving, from the third computer system, metadata associated with thetransaction, wherein: the metadata comprises an indication that thetransaction was successful; and in response to providing the metadata tothe first computer system, the third computer system deletes the privateinformation; and in response to receiving the metadata, the firstcomputer system providing at least one of one or more goods and one ormore services to the citizen of the second jurisdiction, based on themetadata.
 9. The method of claim 8, wherein the program instructionsthat executes the transaction include a branded look and feel.
 10. Themethod of claim 8, wherein the privacy law includes a requirement thatthe transaction that involves the private information of a citizen ofthe second jurisdiction occurs within the second jurisdiction.
 11. Themethod of claim 8, wherein the first computer system providing, to thethird computer system, the at least one of the container and the virtualmachine includes the first computer system providing the at least one ofthe container and the virtual machine to a fourth computer system thatstores the at least one of the container and the virtual machine andprovides the container to the third computer system.
 12. The method ofclaim 8, wherein the first computer system receiving the request for thetransaction from the second computer system in the second jurisdictioncomprises determining that the second jurisdiction is subject to theprivacy law, based on metadata of the request.
 13. The method of claim8, wherein the second computer system and the third computer systemcommunicate via a network within the second jurisdiction.
 14. The methodof claim 8, wherein the metadata includes a transaction identification,a receipt, and/or time information.
 15. A non-transitorycomputer-readable memory medium that stores instructions executable by aprocessor of a system in a first jurisdiction, wherein when theprocessor executes the instructions, the system: receives a request fora transaction that involves a citizen of a second jurisdiction from asecond computer system; determines that the second computer system is ina second jurisdiction, wherein determining that the second computersystem is in the second jurisdiction comprises receiving a networkaddress of the second computer system; determines that the secondjurisdiction is subject to a privacy law; in response to determiningthat the second jurisdiction is subject to the privacy law: selects,from a plurality of computer systems in the second jurisdiction, a thirdcomputer system, in the second jurisdiction, to execute the transaction;provides, to the third computer system, in the second jurisdiction, atleast one of a container and a virtual machine that includes programinstructions to execute the transaction; provides an instruction to thethird computer system to execute the program instructions that executesthe transaction, wherein: in response to executing the programinstructions that execute the transaction, the third computer systemreceives private information from the second computer system and usesthe private information to complete the transaction; receives, from thethird computer system, metadata associated with the transaction,wherein: the metadata comprises an indication that the transaction wassuccessful; and in response to providing the metadata to the system, thethird computer system deletes the private information; and in responseto receiving the metadata, provides at least one of one or more goodsand one or more services to the citizen of the second jurisdiction,based on the metadata.
 16. The non-transitory computer-readable memorymedium of claim 15, wherein the program instructions that executes thetransaction include a branded look and feel.
 17. The non-transitorycomputer-readable memory medium of claim 15, wherein the privacy lawincludes a requirement that the transaction that involves the privateinformation of a citizen of the second jurisdiction occurs within thesecond jurisdiction.
 18. The non-transitory computer-readable memorymedium of claim 15, wherein when the system provides, to the thirdcomputer system, the at least one of the container and the virtualmachine, the system provides the at least one of the container and thevirtual machine to a fourth computer system that stores the at least oneof the container and the virtual machine and provides the container tothe third computer system.
 19. The non-transitory computer-readablememory medium of claim 15, wherein the second computer system and thethird computer system communicate via a network within the secondjurisdiction.
 20. The non-transitory computer-readable memory medium ofclaim 15, wherein the metadata includes a transaction identification, areceipt, and/or time information.